This development kit has the information you will need to begin taking advantage of the Display Manger API. The Display Manager 1.0 API was first introduced with the PowerMacs in System 7.1.2 and subsequently shipped in 7.5 and 7.5.1. The Display Manager 2.0 is included in post 7.5.1 systems and is also available as a system extension which is backward compatible to System 7.1. Software licensing information for the Display Manager extension can be found at: <http://developer.apple.com/mkt/swl/>. The Display Library PowerPC runtime library is included in System 7.5.3 and later systems.
The Display Enabler
For most applications there is now little reason to require users to install the Display Enabler extenson if they are running on 7.5.3 or later systems. However, installing the Display Enabler will assure that the latest Display Manager is running. You can get the most up to date Display Manager by using the latest System Software or installing the newest version of the Apple Displays Software located on the software updates web pages at www.apple.com.
Display Manager: Display Manager 2.0 system extension “ Display Enabler” version 2.4.0. Within the Display Enabler is the Display Library with contains the PowerPC runtime code to use the Display Manager 2.0 API. This library is now part of the Display Enabler itself as well as part of System 7.5.3 and later. InterfaceLib contains the Display Manager 1.0 PowerPC runtime glue code.
The Display Enabler version 2.2.2 (shipping in System 7.6.1) added support for DDC aware NDRV video drivers (see separate note on this support). This support allows the Display Manager to ask the video driver for the display's EDID information containing supported video resolutions. The Display Manager then parses this information and presents it to the user interface for user selection.
An additional change of note: whenever a call to DMSaveScreenPrefs is made, the current display configuration is saved (timing and bit depth) along with the current gamma setting for the display. On restart the Display Manager will reset the display setting. Whenever the gamma settings are changed for user persistent reasons, the code making the change should call DMSaveScreenPrefs (0,0,0) to set that new gamma within the display preferences. In System 8.6 and later, the gamma settings are based on ColorSync profiles, so changing the gamma of the machine (and calling DMSaveScreenPrefs) independently of creating/changing a ColorSync profile will cause a gamma/profile missmatch and should be avoided.
Display Manager Sample Code: The sample applications will allow developers to explore the Display Manager API by changing bit depth and screen resolution on multisync displays. In addition, the sample code will show developers how to handle window repositioning when the display configuration changes.
Compiler & Runtime Files: Are available from Universal Interfaces 3.2 and later or Metrowerks CodeWarrior Pro 3 or later.
If you have any bug reports or comments, please don’t hesitate to email. You can report them through the following:
